ci(ubi-rust-builder): Disable provenance generation#1427
Merged
Conversation
This fixes the image build failures occurring since the last couple of days. The issue itself is caused by provenance generation, which produces an image index manifest instead of an image manifest as before. This then causes the `docker manifest create` command to fail, because it cannot create index manifests out of other index manifests, only normal image manifests. It seems like that a newer Docker version enabled provenance generation by default. This GHA workflow does NOT pin the exact docker (and builder) version we use, which seems like the reason why this issue started popping up without any changes to the workflow or the Dockerfile for these images. Going forward, we should pin the exact Docker version we want to use. This will be done in a separate PR. For now we chose to disable provenance entirely even though we want to use it in general. However, we decided to deal with this once we start to actively work on provenance across our platform.
Techassi
moved this from Development: In Progress
to Development: Waiting for Review
in Stackable Engineering
dervoeti
approved these changes
Feb 16, 2026
Techassi
moved this from Development: Waiting for Review
to Development: Done
in Stackable Engineering
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Successful test run: https://github.com/stackabletech/docker-images/actions/runs/22057774427
This fixes the image build failures occurring since the last couple of days. The issue itself is caused by provenance generation, which produces an image index manifest instead of an image manifest as before. This then causes the
docker manifest createcommand to fail, because it cannot create index manifests out of other index manifests, only normal image manifests.It seems like that a newer Docker version enabled provenance generation by default. This GHA workflow does NOT pin the exact docker (and builder) version we use, which seems like the reason why this issue started popping up without any changes to the workflow or the Dockerfile for these images. Going forward, we should pin the exact Docker version we want to use. This will be done in a separate PR.
For now we chose to disable provenance entirely even though we want to use it in general. However, we decided to deal with this once we start to actively work on provenance across our platform.
References: